Item level data aggregation

ABSTRACT

Apparatuses, systems, methods, and computer program products are disclosed for item level data aggregation. A method includes identifying a transaction made with a third party within a set of transactions. A method includes using electronic credentials for a user to login to an account of the user at a third party. A method includes downloading item-level data from a third party that corresponds to an identified transaction in response to logging into a user&#39;s account at a third party. Item-level data identifies one or more items within an identified transaction. A method includes displaying a set of transactions to a user. A method includes displaying item-level data for one or more items within an identified transaction to a user in response to receiving input from the user relative to the identified transaction in a displayed set of transactions.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/447,106 entitled “ITEM LEVEL DATA AGGREGATION” and filed on Mar. 1,2017 for John Ryan Caldwell, which claims the benefit of U.S.Provisional Patent Application No. 62/302,049 entitled “ITEM LEVEL DATAAGGREGATION” and filed on Mar. 1, 2016 for John Ryan Caldwell, which isincorporated herein by reference in its entirety for all purposes.

FIELD

This invention relates to data aggregation and more particularly relatesto aggregating data at an item level.

BACKGROUND

As more and more of a user's data moves to the cloud, and more and moreevents or transactions become electronic, it has become increasinglydifficult for a user to manage and/or track the user's own personaldata. Users may therefore lose access to the data as services fail ordata expires, or may not be able to access related data stored bydifferent service providers.

SUMMARY

Methods are presented for item level data aggregation. In oneembodiment, a method includes identifying a transaction made with athird party within a set of transactions. A method, in a furtherembodiment, includes using electronic credentials for a user to login toan account of the user at a third party. In certain embodiments, amethod includes downloading item-level data from a third party thatcorresponds to an identified transaction in response to logging into auser's account at a third party. Item-level data identifies one or moreitems within an identified transaction. In a further embodiment, amethod includes displaying a set of transactions to a user. A method, incertain embodiments, includes displaying item-level data for one or moreitems within an identified transaction to a user in response toreceiving input from the user relative to the identified transaction ina displayed set of transactions.

Apparatuses are presented for item level data aggregation. An apparatus,in one embodiment, includes a trusted hardware device authorized by auser to use a plurality of electronic credentials for the user. Atrusted hardware device, in some embodiments, is configured to identifya transaction made with a third party within a set of transactions. In afurther embodiment, a trusted hardware device is configured to useelectronic credentials for a user to login to an account of the user ata third party. A trusted hardware device, in certain embodiments, isconfigured to download item-level data from a third party thatcorresponds to an identified transaction in response to logging into auser's account at the third party. Item-level data identifies one ormore items within an identified transaction. In one embodiment, atrusted hardware device is configured to display a set of transactionsto a user. A trusted hardware device, in a further embodiment, isconfigured to display item-level data for one or more items within anidentified transaction to a user in response to receiving input from theuser relative to the identified transaction in the displayed set oftransactions.

Systems are presented for item level data aggregation. In oneembodiment, a system includes a backend hardware server. A backendhardware server, in certain embodiments, identifies a transaction madewith a third party within a set of transactions. In a furtherembodiment, a backend hardware server uses electronic credentials for auser to login to an account of the user at a third party. A backendhardware server, in one embodiment, downloads item-level data from thethird party that corresponds to the identified transaction in responseto logging into the user's account at the third party. In someembodiments, a backend hardware server downloads item-level data for aplurality of transactions of a user from a hardware server of a thirdparty. Item-level data identifies one or more items within an identifiedtransaction.

A system, in a further embodiment, includes an aggregation modulelocated on a hardware device for a user. An aggregation module, incertain embodiments, comprises one or more of logic hardware and anon-transitory computer readable storage medium storing computerexecutable code. In one embodiment, an aggregation module is configuredto display a set of transactions to the user. An aggregation module, insome embodiments, is configured to display the item-level data for oneor more items within an identified transaction to a user in response toreceiving input from the user relative to the identified transaction ina displayed set of transactions.

An apparatus, in another embodiment, includes means for performing thevarious steps and operations described with regard to the disclosedmethods, apparatuses, and systems. Computer program products comprisinga computer readable storage medium are presented. In certainembodiments, a computer readable storage medium stores computer usableprogram code executable to perform one or more of the operationsdescribed with regard to the disclosed methods, apparatuses, andsystems.

BRIEF DESCRIPTION OF THE DRAWINGS

In order that the advantages of the invention will be readilyunderstood, a more particular description of the invention brieflydescribed above will be rendered by reference to specific embodimentsthat are illustrated in the appended drawings. Understanding that thesedrawings depict only typical embodiments of the invention and are nottherefore to be considered to be limiting of its scope, the inventionwill be described and explained with additional specificity and detailthrough the use of the accompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of asystem for item level data aggregation;

FIG. 2 is a schematic block diagram of one embodiment of an aggregationmodule;

FIG. 3 is a schematic block diagram of another embodiment of anaggregation module;

FIG. 4A is a schematic block diagram illustrating an additionalembodiment of a system for item level data aggregation;

FIG. 4B is a schematic block diagram illustrating a further embodimentof a system for item level data aggregation;

FIG. 4C is a schematic block diagram illustrating a certain embodimentof a system for item level data aggregation;

FIG. 5A is a schematic block diagram illustrating one embodiment of auser interface;

FIG. 5B is a schematic block diagram illustrating another embodiment ofa user interface;

FIG. 6A is a schematic block diagram illustrating one embodiment of anaggregated set of transactions and item-level data for transactions;

FIG. 6B is a schematic block diagram illustrating one embodiment of agraphical user interface; and

FIG. 7 is a schematic flow chart diagram illustrating a furtherembodiment of a method for item level data aggregation.

DETAILED DESCRIPTION

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusiveand/or mutually inclusive, unless expressly specified otherwise. Theterms “a,” “an,” and “the” also refer to “one or more” unless expresslyspecified otherwise.

Furthermore, the described features, advantages, and characteristics ofthe embodiments may be combined in any suitable manner. One skilled inthe relevant art will recognize that the embodiments may be practicedwithout one or more of the specific features or advantages of aparticular embodiment. In other instances, additional features andadvantages may be recognized in certain embodiments that may not bepresent in all embodiments.

These features and advantages of the embodiments will become more fullyapparent from the following description and appended claims, or may belearned by the practice of embodiments as set forth hereinafter. As willbe appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method, and/or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module,” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having program code embodied thereon.

Many of the functional units described in this specification have beenlabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom VLSI circuits or gate arrays,off-the-shelf semiconductors such as logic chips, transistors, or otherdiscrete components. A module may also be implemented in programmablehardware devices such as field programmable gate arrays, programmablearray logic, programmable logic devices or the like.

Modules may also be implemented in software for execution by varioustypes of processors. An identified module of program code may, forinstance, comprise one or more physical or logical blocks of computerinstructions which may, for instance, be organized as an object,procedure, or function. Nevertheless, the executables of an identifiedmodule need not be physically located together, but may comprisedisparate instructions stored in different locations which, when joinedlogically together, comprise the module and achieve the stated purposefor the module.

Indeed, a module of program code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different storage devices, and may exist, atleast partially, merely as electronic signals on a system or network.Where a module or portions of a module are implemented in software, theprogram code may be stored and/or propagated on in one or more computerreadable medium(s).

The computer program product may include a computer readable storagemedium (or media) having computer readable program instructions thereonfor causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (“RAM”), aread-only memory (“ROM”), an erasable programmable read-only memory(“EPROM” or Flash memory), a static random access memory (“SRAM”), aportable compact disc read-only memory (“CD-ROM”), a digital versatiledisk (“DVD”), a memory stick, a floppy disk, a mechanically encodeddevice such as punch-cards or raised structures in a groove havinginstructions recorded thereon, and any suitable combination of theforegoing. A computer readable storage medium, as used herein, is not tobe construed as being transitory signals per se, such as radio waves orother freely propagating electromagnetic waves, electromagnetic wavespropagating through a waveguide or other transmission media (e.g., lightpulses passing through a fiber-optic cable), or electrical signalstransmitted through a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and computerprogram products according to various embodiments of the presentinvention. In this regard, each block in the schematic flowchartdiagrams and/or schematic block diagrams may represent a module,segment, or portion of code, which comprises one or more executableinstructions of the program code for implementing the specified logicalfunction(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and program code.

FIG. 1 depicts one embodiment of a system 100 for item level dataaggregation. In one embodiment, the system 100 includes one or morehardware devices 102, one or more aggregation modules 104 (e.g., abackend aggregation module 104 b and/or a plurality of aggregationmodules 104 a disposed on the one or more hardware devices 102), one ormore data networks 106 or other communication channels, one or morethird party service providers 108 (e.g., one or more servers 108 of oneor more service providers 108; one or more cloud or network serviceproviders 108, or the like), and/or one or more backend hardware servers110. In certain embodiments, even though a specific number of hardwaredevices 102, aggregation modules 104, data networks 106, third partyservice providers 108, and/or backend hardware servers 110 are depictedin FIG. 1, one of skill in the art will recognize, in light of thisdisclosure, that any number of hardware devices 102, aggregation modules104, data networks 106, third party service providers 108, and/orbackend hardware servers 110 may be included in the system 100 fordistributed data aggregation.

In one embodiment, the system 100 includes one or more hardware devices102. The hardware devices 102 (e.g., computing devices, informationhandling devices, or the like) may include one or more of a desktopcomputer, a laptop computer, a mobile device, a tablet computer, a smartphone, a set-top box, a gaming console, a smart TV, a smart watch, afitness band, an optical head-mounted display (e.g., a virtual realityheadset, smart glasses, or the like), an HDMI or other electronicdisplay dongle, a personal digital assistant, and/or another computingdevice comprising a processor (e.g., a central processing unit (CPU), aprocessor core, a field programmable gate array (FPGA) or otherprogrammable logic, an application specific integrated circuit (ASIC), acontroller, a microcontroller, and/or another semiconductor integratedcircuit device), a volatile memory, and/or a non-volatile storagemedium. In certain embodiments, the hardware devices 102 are incommunication with one or more servers 108 of one or more third partyservice providers 108 and/or one or more backend hardware servers 110via a data network 106, described below. The hardware devices 102, in afurther embodiment, are capable of executing various programs, programcode, applications, instructions, functions, or the like.

In one embodiment, an aggregation module 104 is configured to determineand/or receive a user's electronic credentials (e.g., username andpassword, fingerprint scan, retinal scan, digital certificate, personalidentification number (PIN), challenge response, security token,hardware token, software token, DNA sequence, signature, facialrecognition, voice pattern recognition, bio-electric signals, two-factorauthentication credentials, or the like) for one or more third partyservice providers 108. The aggregation module 104, in certainembodiments, accesses a server 108 of a third party service provider 108using a user's electronic credentials to download data associated withthe user from the server 108, such as a user's purchase history, auser's photos, a user's social media posts, a user's medical records, auser's financial transaction records or other financial data, and/orother data associated with and/or owned by a user but stored by a server108 of a third party service provider 108 (e.g., stored by hardware notowned, maintained, and/or controlled by the user). The aggregationmodule 104, in various embodiments, may provide the downloaded data tothe user locally (e.g., displaying the data on an electronic display ofa hardware device 102); may provide the downloaded data from thehardware device 102 of the user to a remote server 110 (e.g., a backendaggregation module 104 b) which may be unaffiliated with the third partyservice provider 108; may provide one or more alerts, messages,advertisements, or other communications to the user (e.g., on a hardwaredevice 102) based on the downloaded data; or the like.

In certain embodiments, the system 100 includes a plurality ofaggregation modules 104 disposed/located on hardware devices 102 of aplurality of different users (e.g., comprising hardware of and/orexecutable code running on one or more hardware devices 102). Theplurality of aggregation modules 104 may act as a distributed and/ordecentralized system 100, executing across multiple hardware devices102, which are geographically dispersed and using different IPaddresses, each downloading and/or aggregating data (e.g., photos,social media posts, medical records, financial transaction records,other financial data, and/or other user data) separately, in adistributed and/or decentralized manner. While a third party serviceprovider 108 (e.g., an ecommerce site or other online retailer orservice provider; a financial institution, bank, credit union, and/orother online banking provider; a social media site; a medical provider;a photo hosting site; or the like) may block a data aggregation serviceor other entity from accessing data for a plurality of users from asingle location (e.g., a single IP address, a single block of IPaddresses, or the like), a distributed and/or decentralized swarm ofmany aggregation modules 104, in certain embodiments, may be much moredifficult for a third party service provider 108 to block.

In one embodiment, a hardware device 102 may include and/or execute aninternet browser, which a user may use to access a server 108 of a thirdparty service provider 108 (e.g., by loading a webpage of the thirdparty service provider 108 in the internet browser). At least a portionof an aggregation module 104, in certain embodiments, may comprise aplugin to and/or an extension of an internet browser of a user'spersonal hardware device 102, so that a third party service provider 108may not block the aggregation module 104 from accessing the server 108of the third party service provider 108 without also blocking the user'sown access to the server 108 using the internet browser. For example,the aggregation module 104 may use the same cookies, IP address, savedcredentials, or the like as a user would when accessing a server 108 ofa third party service provider 108 through the internet browser. Incertain embodiments, the aggregation module 104 may support integrationwith multiple different types of internet browsers (e.g., on differenthardware devices 102).

An aggregation module 104, in certain embodiments, may mimic or copy auser's behavioral pattern in accessing a server 108 of a third partyservice provider 108, to reduce a likelihood that the third partyservice provider 108 may distinguish access to the server 108 by anaggregation module 104 from access to the server 108 by a user. Forexample, an aggregation module 104 may visit one or more locations(e.g., webpages) of a server 108 of a third party service provider 108,even if the aggregation module 104 does not intend to download data fromeach of the one or more locations, may wait for a certain delay timebetween accessing different locations, may use a certain scroll pattern,or the like, to mask the aggregation module 104's downloading and/oraggregating of a user's data, to reduce the chances of being detectedand/or blocked by the third party service provider 108.

In one embodiment, at least a portion of an aggregation module 104 maybe integrated with or otherwise part of another application executing ona hardware device 102, such as a personal financial managementapplication (e.g., computer executable code for displaying a user'sfinancial transactions from multiple financial institutions includingitem level purchase details within single transactions, determiningand/or displaying a user's financial budgets and/or financial goals,determining and/or displaying a user's account balances, determiningand/or displaying a user's net worth, or the like), a photo viewer, amedical application, an insurance application, an accountingapplication, a social media application, or the like, which may use datathe aggregation module 104 downloads from a server 108 of a third partyservice provider 108.

In one embodiment, the aggregation modules 104 a comprise a distributedsystem 100, with the aggregation modules 104 a and/or the associatedhardware devices 102 downloading and/or aggregating data substantiallyindependently (e.g., downloading data concurrently or non-concurrently,without a global clock, with independent success and/or failure ofcomponents). Distributed aggregation modules 104 a may pass messages toeach other and/or to a backend aggregation module 104 b, to coordinatetheir distributed aggregation of data for users. In one embodiment, theaggregation modules 104 a are decentralized (e.g., hardware devices 102associated with users perform one or more aggregation functions such asdownloading data), rather than relying exclusively on a centralizedserver or other device to perform one or more aggregation functions.

In a distributed and/or decentralized system 100, a central entity, suchas a backend aggregation module 104 b and/or a backend hardware server110, in certain embodiments, may still provide, to one or moreaggregation modules 104 a, one or more messages comprising instructionsfor accessing a server 108 of a third party service provider 108 using auser's credentials, or the like. For example, a backend aggregationmodule 104 b may provide one or more aggregation modules 104 a of one ormore hardware devices 102 with one or more sets of instructions foraccessing a server 108 of a third party service 108, such as a locationfor entering a user's electronic credentials (e.g., a text box, a field,a label, a coordinate, or the like), an instruction for submitting auser's electronic credentials (e.g., a button to press, a link to click,or the like), one or more locations of data associated with a user(e.g., a row in a table or chart, a column in a table or chart, auniform resource locator (URL) or other address, a coordinate, a label,or the like), and/or other instructions or information, using which theaggregation modules 104 a may access and download a user's data.

In a further embodiment, one or more aggregation modules 104 a may passmessages to each other, such as instructions for accessing a server 108of a third party service provider 108 using a user's credentials, or thelike, in a peer-to-peer manner. In another embodiment, a central entity,such as a backend aggregation module 104 b, may initially seed one ormore sets of instructions for accessing a server 108 of a third partyservice provider 108 using a user's credentials to one or moreaggregation modules 104 a, and the one or more aggregation modules 104 amay send the one or more sets of instructions to other aggregationmodules 104 a.

Instructions for accessing a user's data, however, in certainembodiments, may change over time, may vary for different users of athird party service provider 108, or the like (e.g., due to upgrades,different service levels or servers 108 for different users,acquisitions and/or consolidation of different third party serviceproviders 108, or the like), causing certain instructions to fail overtime and/or for certain users, preventing an aggregation module 104 fromaccessing and downloading a user's data. A backend aggregation module104 b, in one embodiment, may provide one or more aggregation modules104 a with a hierarchical list of multiple sets of instructions, knownto have enabled access to a user's data from a server 108 of a thirdparty service provider 108. An aggregation module 104 a on a hardwaredevice 102 may try different sets of instructions in hierarchical order,until the aggregation module 104 a is able to access a user's data.

An aggregation module 104, in certain embodiments, may provide aninterface to a user allowing the user to repair or fix failedinstructions for accessing the user's data, by graphically identify aninput location for the user's electronic credentials, an instruction forsubmitting a user's electronic credentials, a location of dataassociated with the user, or the like. An aggregation module 104, in oneembodiment, may highlight or otherwise suggest (e.g., bold, color,depict a visual comment or label, or the like) an estimate which theaggregation module 104 has determined of an input location for theuser's electronic credentials, an instruction for submitting a user'selectronic credentials, a location of data associated with the user, orthe like. For example, an aggregation module 104 may process a web pageof a server 108 of a third party service provider 108 (e.g., parseand/or search a hypertext markup language (HTML) file) to estimate aninput location for the user's electronic credentials, an instruction forsubmitting a user's electronic credentials, a location of dataassociated with the user, or the like.

An aggregation module 104, in certain embodiments, may provide anadvanced interface for a user to graphically repair broken and/or failedinstructions for accessing a user's data from a server 108 of a thirdparty service provider 108, which allows a user to view code of awebpage (e.g., HTML or the like) and to identify an input location forthe user's electronic credentials, an instruction for submitting auser's electronic credentials, a location of data associated with theuser, or the like within the code of the webpage. In one embodiment, anaggregation module 104 may provide a basic interface for a user tographically repair broken and/or failed instructions for accessing auser's data from a server 108 of a third party service provider 108 byoverlaying a basic interface over a web page or other location of theserver 108 wherein the user may graphically identify an input locationfor the user's electronic credentials, an instruction for submitting auser's electronic credentials, a location of data associated with theuser, or the like (e.g., without requiring the user to view HTML orother code of the web page). An aggregation module 104, in certainembodiments, may provide an interface that includes a selectable list ofbroken and/or missing instructions, locations, or the like, and mayhighlight and/or display suggestions graphically in response to a userselecting an item from the list.

An aggregation module 104, in one embodiment, may test instructionsprovided by users (e.g., using a test set) before allowing each of theaggregation modules 104 a to use the provided instructions (e.g., toprevent an abusive user from providing false or incorrect instructions).An aggregation module 104 may score or rate users based on a successrate of the users' provided instructions, and may expedite (e.g.,provide to a greater number of aggregation modules 104 a and/or users)the use of instructions from users with a higher score or rating. Thedistributed network of aggregation modules 104, in certain embodiments,may thereby be self-healing and/or self-testing, allowing continuedaccess to and/or aggregation of users' data from one or more third partyservice providers 108, even if access instructions change or becomebroken.

The one or more aggregation modules 104, in certain embodiments, mayprovide an interface (e.g., an application programming interface (API))to provide downloaded and/or aggregated user data from servers 108 ofone or more third party service providers 108 to one or more otherentities (e.g., a remote server 110 unaffiliated with the third partyservice provider 108, a backend aggregation module 104 b, or the like).The interface, in one embodiment, comprises a private interface betweenaggregation modules 104 a of users' hardware devices 102 and one or morebackend aggregation modules 104 b. For example, this may enable abackend aggregation module 104 b to provide a user with access todownloaded and/or aggregated user data at multiple locations, onmultiple hardware devices 102, through multiple channels, or the like,even if the user's hardware device 102 which downloaded the data isturned off, out of battery, not connected to the data network 106, orthe like. In another embodiment, the interface comprises a public and/oropen interface, which may be secured, allowing a user to share theuser's downloaded data from an aggregation module 104 to one or moreother tools, services, and/or other entities to store, process, and/orotherwise use the data.

In various embodiments, an aggregation module 104 may be embodied ashardware, software, or some combination of hardware and software. In oneembodiment, an aggregation module 104 may comprise executable programcode stored on a non-transitory computer readable storage medium forexecution on a processor of a hardware device 102, a backend hardwareserver 110, or the like. For example, an aggregation module 104 may beembodied as executable program code executing on one or more of ahardware device 102, a backend hardware server 110, a combination of oneor more of the foregoing, or the like. In such an embodiment, thevarious modules that perform the operations of an aggregation module104, as described below, may be located on a hardware device 102, abackend hardware server 110, a combination of the two, and/or the like.

In various embodiments, an aggregation module 104 may be embodied as ahardware appliance that can be installed or deployed on a backendhardware server 110, on a user's hardware device 102 (e.g., a dongle, aprotective case for a phone 102 or tablet 102 that includes one or moresemiconductor integrated circuit devices within the case incommunication with the phone 102 or tablet 102 wirelessly and/or over adata port such as USB or a proprietary communications port, or anotherperipheral device), or elsewhere on the data network 106 and/orcollocated with a user's hardware device 102. In certain embodiments, anaggregation module 104 may comprise a hardware device such as a securehardware dongle or other hardware appliance device (e.g., a set-top box,a network appliance, or the like) that attaches to another hardwaredevice 102, such as a laptop computer, a server, a tablet computer, asmart phone, or the like, either by a wired connection (e.g., a USBconnection) or a wireless connection (e.g., Bluetooth®, Wi-Fi®,near-field communication (NFC), or the like); that attaches to anelectronic display device (e.g., a television or monitor using an HDMIport, a DisplayPort port, a Mini DisplayPort port, VGA port, DVI port,or the like); that operates substantially independently on a datanetwork 106; or the like. A hardware appliance of an aggregation module104 may comprise a power interface, a wired and/or wireless networkinterface, a graphical interface (e.g., a graphics card and/or GPU withone or more display ports) that outputs to a display device, and/or asemiconductor integrated circuit device as described below, configuredto perform the functions described herein with regard to an aggregationmodule 104.

An aggregation module 104, in such an embodiment, may comprise asemiconductor integrated circuit device (e.g., one or more chips, die,or other discrete logic hardware), or the like, such as afield-programmable gate array (FPGA) or other programmable logic,firmware for an FPGA or other programmable logic, microcode forexecution on a microcontroller, an application-specific integratedcircuit (ASIC), a processor, a processor core, or the like. In oneembodiment, an aggregation module 104 may be mounted on a printedcircuit board with one or more electrical lines or connections (e.g., tovolatile memory, a non-volatile storage medium, a network interface, aperipheral device, a graphical/display interface. The hardware appliancemay include one or more pins, pads, or other electrical connectionsconfigured to send and receive data (e.g., in communication with one ormore electrical lines of a printed circuit board or the like), and oneor more hardware circuits and/or other electrical circuits configured toperform various functions of an aggregation module 104.

The semiconductor integrated circuit device or other hardware applianceof an aggregation module 104, in certain embodiments, comprises and/oris communicatively coupled to one or more volatile memory media, whichmay include but is not limited to: random access memory (RAM), dynamicRAM (DRAM), cache, or the like. In one embodiment, the semiconductorintegrated circuit device or other hardware appliance of an aggregationmodule 104 comprises and/or is communicatively coupled to one or morenon-volatile memory media, which may include but is not limited to: NANDflash memory, NOR flash memory, nano random access memory (nano RAM orNRAM), nanocrystal wire-based memory, silicon-oxide based sub-10nanometer process memory, graphene memory,Silicon-Oxide-Nitride-Oxide-Silicon (SONOS), resistive RAM (RRAM),programmable metallization cell (PMC), conductive-bridging RAM (CBRAM),magneto-resistive RAM (MRAM), dynamic RAM (DRAM), phase change RAM (PRAMor PCM), magnetic storage media (e.g., hard disk, tape), optical storagemedia, or the like.

The data network 106, in one embodiment, includes a digitalcommunication network that transmits digital communications. The datanetwork 106 may include a wireless network, such as a wireless cellularnetwork, a local wireless network, such as a Wi-Fi network, a Bluetooth®network, a near-field communication (NFC) network, an ad hoc network,and/or the like. The data network 106 may include a wide area network(WAN), a storage area network (SAN), a local area network (LAN), anoptical fiber network, the internet, or other digital communicationnetwork. The data network 106 may include two or more networks. The datanetwork 106 may include one or more servers, routers, switches, and/orother networking equipment. The data network 106 may also include one ormore computer readable storage media, such as a hard disk drive, anoptical drive, non-volatile memory, RAM, or the like.

The one or more third party service providers 108, in one embodiment,may include one or more network accessible computing systems such as oneor more web servers hosting one or more web sites, an enterpriseintranet system, an application server, an application programminginterface (API) server, an authentication server, or the like. The oneor more third party service providers 108 may include systems related tovarious institutions or organizations. For example, a third partyservice provider 108 may include a system providing electronic access toan ecommerce site or other online retailer or service provider, afinancial institution, a university, a government agency, a utilitycompany, an email provider, a social media site, a photo sharing site, avideo sharing site, a data storage site, a medical provider, or anotherentity that stores data associated with a user. A third party serviceprovider 108 may allow users to create user accounts to upload, view,create, and/or modify data associated with the user. Accordingly, athird party service provider 108 may include an authorization system,such as a login element or page of a web site, application, or similarfront-end, where a user can provide credentials, such as ausername/password combination, to access the user's data.

In one embodiment, the one or more backend hardware servers 110 and/orone or more backend aggregation modules 104 b provide central managementof the networked swarm of aggregation modules 104 a. For example, theone or more backend aggregation modules 104 b and/or a backend hardwareserver 110 may store downloaded user data from the aggregation modules104 a centrally, may provide instructions for the aggregation modules104 a to access user data from one or more third party service providers108 using user credentials, or the like. A backend hardware server 110may include one or more servers located remotely from the hardwaredevices 102 and/or the one or more third party service providers 108. Abackend hardware server 110 may include at least a portion of themodules or sub-modules described below with regard to the aggregationmodules 104 of FIG. 2 and FIG. 3, may comprise hardware of anaggregation module 104, may store executable program code of anaggregation module 104 in one or more non-transitory computer readablestorage media, and/or may otherwise perform one or more of the variousoperations of an aggregation module 104 described herein in order toaggregate user data from one or more third party service providers in adistributed manner.

In certain embodiments, a user 102 may provide electronic credentials toan aggregation module 104 in order for the aggregation module 104 todownload and/or aggregate the user's data from an associated accountwith one or more third party service providers 108; in order for theaggregation module 104 to change, transfer, or switch periodic and/orrecurring payments (e.g., bill pay, credit or debit card payments,automated clearing house (ACH) payments, or the like) made to a thirdparty service provider 108 to a different payment provider (e.g., adifferent bank, credit union, or other financial institution; adifferent credit or debit card; a different bank account; or the like);and/or for another purpose.

The aggregation module 104, in one embodiment, downloads and/oraggregates item level data from one or more third party serviceproviders 110. In certain embodiments, item level data comprisesidentification of one or more sub-items that form part of a larger item.For example, item level data may comprise identifiers for one or moreindividual items (e.g., goods and/or services) which a user purchasedwithin a larger, single transaction. An item level identifier for one ormore individual items may include one or more of the item's name, stockkeeping unit (SKU) identifier, universal product code (UPC),international article number (EAN), global trade item number (GTIN), orthe like.

Item level data, in certain embodiments, may not be available fromcertain third party service providers 108. For example, a financialinstitution 108 may provide the aggregation module 104 with a list ofone or more transactions, including one or more of a date, an amount, alocation or vendor, or the like for each transaction, but without anyitem level information for items within a transaction. In order todownload and/or aggregate item level data, in one embodiment, theaggregation module 104 may use a user's electronic credentials to accessa third party service provider 108 associated with an identifiedtransaction, such as an online shopping website; an audio, video, and/orother digital media website; a loyalty and/or rewards website for aretail store; or the like, to access and download item level informationfor items within a transaction (e.g., by accessing the user's purchasehistory, transaction history, order history, account history, viewing orlistening history, or the like).

For example, the aggregation module 104 may download item level datacomprising movies and/or television shows purchased and/or viewed,eBooks purchased and/or read, or the like from a digital mediaprovider's website, such as Apple® iTunes®, Google® Play®, Netflix®,Hulu®, Amazon®, or the like. The aggregation module 104 may downloaditem level data comprising physical goods or other items purchased froman online retailer's website, such as Amazon® or the like. Theaggregation module 104 may download item level data comprising menuitems ordered from a restaurant's loyalty and/or rewards website; maydownload item level data for individual goods purchased from a grocerystore, department store, hardware store, or the like's loyalty and/orrewards website, from a store credit card account website, or the like.

The aggregation module 104 may automatically click or select one or moreindividual items within a listed history, and download the resultingitem level data for the item, returning to the listed history andrepeating for each listed item or the like, using an access patternand/or screen scrape as described in greater detail below. In certainembodiments, in response to determining that item level data for atransaction is not available from a third party service provider 108and/or in response to a request from a user, the aggregation module 104may use a camera of a hardware device 102, a scanner, or the like tophotograph and/or scan a paper receipt from a third party serviceprovider 108, and may use optical character recognition to determineitem level data from the receipt, instead of and/or in addition todownloading item level data from one or more third party serviceproviders 108.

In one embodiment, the aggregation module 104 may correlate downloadedand/or aggregated transaction data that does not have item level data(e.g., from a financial institution, from a financial transaction dataaggregation server 104 b, or the like) with item level data downloadedand/or aggregated from a particular third party service provider 108with which the transaction occurred. For example, the aggregation module104 may match a location and/or vendor identifier or portion thereoflisted in transaction data, with the actual third party service provider108 with which the transaction occurred, access item level data from thethird party service provider 108, and match the transaction data to theitem level data based on a transaction amount, a transaction date, atransaction location, a product image, a product link, a number ofitems, or the like. The aggregation module 104 may present the itemlevel data to the user within a personal financial management interface,allowing the user to view a transaction history, with item level datafor individual transactions, may categorize a transaction (e.g., forinclusion in a budget or the like) based on the item level data, mayprovide a recommendation and/or advertisement based on the item leveldata, and/or otherwise provide the item level data to the user.

In one embodiment, an aggregation module 104 is configured to switch,migrate, and/or transfer execution of one or more transactions betweenservice providers 108. An aggregation module 104 may identify atransaction to migrate by processing aggregated data (e.g., anaggregated set of transactions) from one or more servers 108 (e.g.,downloaded from one or more third party service providers 108, from oneor more first party service providers 108 associated with the backendserver 110, from one or more aggregation servers 108, and/or the like).An aggregation module 104 may identify one or more repeatingtransactions from a set of transactions, prompt a user to migrate one ormore repeating transactions from one service provider 108 to a differentservice provider 108, and/or migrate one or more repeating transactionsto a different service provider 108, or the like.

Many users may desire to switch service providers 108. However, serviceproviders 108 may make the process difficult, or users may not want togo through the headache of making the switch, even if a differentservice provider 108 provides better features, quality, price, oranother attribute than a current service provider 108. An aggregationmodule 104, in certain embodiments, identifies repeating transactionsassociated with a service provider 108, and provides an interfaceallowing a user to switch or migrate the transaction to a differentservice provider 108 (e.g., a different software as a service (SaaS)provider; a different data repository; a different social network; adifferent payment source such as a debit card, credit card, financialaccount, online payment system account, or the like; a different entityand/or institution; or the like).

An aggregation module 104 may comprise and/or be part of a trustedhardware device 102, 110, which is secure and authorized by a user tostore and/or use one or more of the user's electronic credentials orother important data. An aggregation module 104 may be provided by agovernment entity, an educational institution, a financial institution,and/or another entity which the user trusts and/or authorizes to act inits behalf. For example, an aggregation module 104 may be provided by aservice provider 108 associated with the backend server 110, allowingusers to migrate and/or switch one or more transactions from other thirdparty service providers 108 to the first party service provider 108providing the aggregation module 104 (e.g., a social network 108'sapplication or website may provide an aggregation module 104 as abrowser plugin, a mobile application, installable software, or the likethat prompts a user to migrate and/or switch a social media post to thesocial network, in response to identifying repeated posts to a differentsocial network; a financial institution 108's mobile application and/orwebsite may prompt a user to switch one or more repeating payments froma credit card, debit card, checking account, savings account, or otherfinancial account of a competitor 108 to a credit card, debit card,checking account, savings account, or other financial account of thefinancial institution 108; an operating system for a hardware device 102may comprise an aggregation module 104 that identifies repeatingantivirus scans, data backups, or other events/transactions, and mayprompt a user to migrate and/or switch the identified transactions froma third party service provider 108 to a service provider 108 associatedwith the operating system; or the like).

In this manner, one or more aggregation modules 104 may automate and/orsimplify the migration of transactions from one service provider 108 toa different service provider 108, with minimal interaction with a user(e.g., accepting a prompt, providing and/or authorizing use ofelectronic credentials, or the like), rather than requiring a user tocontact a service provider 108 to manually migrate or transfer executionof an event/transaction.

A transaction, as used herein, may comprise a detected and/or recordedelectronic occurrence or the like associated with a user, a user'shardware device 102, a user's account, or the like. A transaction, invarious embodiments, may occur on and/or may be detected and/or recordedby an aggregation module 104, a service provider 108, a backend server110, a hardware device 102 of a user, one or more sensors, or the like.For example, in various embodiments, a transaction may comprise one ormore of a data backup event for a hardware device 102 of a user over adata network 106 (e.g., to a service provider 108), an antivirus and/orsecurity scan event for a hardware device 102 of a user (e.g.,periodically scanning files and/or data storage of a hardware device 102to locate one or more viruses, malware, bots, worms, rootkits, and/orother security risks using software and/or definitions provided by oneor more service providers 108), a software and/or firmware update eventfor a hardware device 102 of a user (e.g., an operating system update, asoftware patch, an application update, and/or another update downloadedand/or installed from a service provider 108 over a data network 106),an electronic subscription event for a data network service (e.g., arenewal, a payment, or the like), an electronic transaction event (e.g.,a credit or debit card payment, a direct deposit, an electronic billpayment, an automated clearing house (ACH) payment, an online and/orelectronic money transfer, a mobile and/or wireless payment, or the liketo a website, merchant, vendor, individual, and/or other entity), or thelike.

A subscription event may include renewing a subscription, paying for asubscription, or the like. A data network service may comprise a digitaland/or electronic service that may occur over and/or using a datanetwork 106, such as a cloud software and/or software as a service(SaaS) subscription, a streaming and/or downloadable media subscription(e.g., video, audio, e-books, or the like), an internet servicesubscription, a cable television subscription, a subscription made overa data network 106 for delivery of digital and/or physical goods and/orservices, or the like.

A repeating transaction may comprise an event that occurs more thanonce. Different occurrences of a repeating transaction, in certainembodiments, may comprise at least one attribute in common (e.g., and/ormay have one or more attributes that are different). For example,different occurrences of a repeating transaction may be associated withthe same service provider 108, website, and/or other entity; may occuron or around the same time, periodically (e.g., at or around the sametime each day; on the same day and/or within a few days each week,month, quarter, year, or other time period; or the like); may beassociated with the same or similar (e.g., within a predefinedpercentage or amount) transaction amount; and/or have one or more othersimilarities. An aggregation module 104 may be configured to select oneor more repeating transactions having at least a threshold number ofsimilarities, may only select one or more repeating transactions havingone or more required similarities, or the like. In one embodiment, anaggregation module 104 may provide an interface (e.g., a graphical userinterface (GUI), an application programming interface (API), a commandline interface (CLI), and/or another interface) allowing a user (e.g.,an end user on a hardware device 102, an administrator of a backendserver 110, or the like) to select or otherwise define one or more rulesfor the aggregation module 104 to identify one or more repeatingtransactions, such as a rule defining a threshold number of similaritiesfor a repeated transaction, a rule requiring one or more similaritiesfor a repeated transaction, a rule allowing one or more differences fora repeated transaction, or the like.

In certain embodiments, a recurring transaction is a type of repeatedtransaction with one or more predefined similarities, such as a repeatedtransaction that occurs on or around the same time during each of aplurality of time periods (e.g., at or around the same time each day; onthe same day and/or within a few days each week, month, quarter, year,or other time period; or the like) and/or is associated with the same orsimilar (e.g., within a predefined percentage or amount) transactionamount, or the like. In one embodiment, an aggregation module 104 may beconfigured to identify any repeating transaction (e.g., includingrecurring and non-recurring events/transactions). In a furtherembodiment, an aggregation module 104 may be configured to identify onlyrecurring events/transactions.

An aggregation module 104, in one embodiment, may download, aggregate,and/or otherwise collect or receive a set of transactions (e.g., a log,a listing, a history, a file, a data structure, and/or another record ofone or more transactions), in which the aggregation module 104 mayidentify one or more repeating transactions or the like for migratingand/or switching. For example, an aggregation module 104 may aggregatetransactions comprising a user's posts to one or more social medianetworks 108, may aggregate system and/or application logs from one ormore hardware devices 102, may aggregate transactions from one or moreelectronic calendar or scheduling services 108, may aggregate imagesfrom one or more image sharing and/or backup services 108, may aggregatefinancial transactions from one or more financial institutions 108, mayaggregate online orders from one or more e-commerce services 108, and/ormay aggregate a set of transactions from one or more servers 102, 108,110.

An aggregation module 104, in certain embodiments, may aggregate a setof transactions from one type of service provider 108 in order toidentify and migrate repeating transactions for another type of serviceprovider 108. For example, an aggregation module 104 may aggregatefinancial transactions from one or more financial institution serviceproviders 108 that have issued debit and/or credit cards to a user;where a user has a checking, savings, or other financial account; or thelike in order to identify repeating transactions for one or more othertypes of service providers 108 (e.g., a SaaS provider, a softwarepublisher, a subscription media provider, an e-commerce website, amerchant, a vendor, a mobile wallet provider, an antivirus provider, autility company, an email provider, a social media site, a photo sharingsite, a video sharing site, a data storage site, a medical provider, orthe like). An aggregation module 104 may use a first set of electroniccredentials of a user to aggregate a set of transactions (e.g., directlyand/or indirectly from one or more financial institutions to aggregatefinancial transaction data comprising financial transaction events) and,in response to identifying a repeated transaction, prompting a user tomigrate the repeated transaction, and receiving authorization from theuser accepting the prompt, the aggregation module 104 may use a secondset of electronic credentials of the user to migrate the repeatedtransaction to a different service provider 108 (e.g., using a user'selectronic credentials for a streaming video service such as Netflix® tochange the default payment source to a credit or debit card associatedwith a different financial institution service provider 108, or thelike).

An aggregation module 104 may be configured to process aggregated and/ordownloaded transaction data and/or item-level data to identify one ormore repeating transactions. For example, an aggregation module 104 mayidentify common and/or similar text strings in records for differentinstances of a repeating transaction (e.g., a text string associatedwith the same service provider 108), may identify a pattern in timing(e.g., time of day, day of the week, day of the month, day of the year,week of the year, month of the year, or the like) based on a timestampor other date record for a repeating transaction, may correlatenumerical values for different instances of a repeating transaction(e.g., the same value or within a threshold amount of the same value;the same monetary amount or within a threshold amount of the samemonetary amount; or the like), may identify a similar transactionidentifier and/or service provider 108 identifier (e.g., a name, URL orother address, or the like), may use artificial intelligence and/ormachine learning to correlate transaction data into one or morerepeating transactions, and/or may otherwise identify one or morerepeating transactions.

A central aggregation module 104 b, in certain embodiments, may processaggregated sets of transactions for multiple users (e.g., each of aservice provider 108's users, or the like) to identify repeatingtransactions and may dynamically target and/or select certain repeatedtransactions for certain users based on the aggregated sets oftransactions. For example, in one embodiment, an aggregation module 104may determine whether or not to prompt a user to migrate a repeatingtransaction (e.g., subsequent instances of a repeating transactionidentified in historical aggregated sets of transaction data) based on alikelihood that an aggregated set of transactions for the user includeseach transaction for the user of an transaction type of the aggregatedset of transactions (e.g., all or substantially all of a user's socialmedia posts from all of the user's social media accounts, all orsubstantially all of a user's financial transactions from all of theuser's financial accounts, or the like). In a further embodiment,instead of and/or in addition to being based on a likelihood that anaggregated set of transactions for the user includes each transactionfor the user of an transaction type, an aggregation module 104 maydetermine whether or not to prompt a user to migrate a repeatingtransaction to a different service provider 108 based on an estimatedvalue to the different service provider 108 of migrating the repeatingtransaction (e.g., of migrating subsequent instances of the repeatingtransaction) based on values associated with the repeated transaction inthe aggregated set of transactions for the user.

In one embodiment, an aggregation module 104 selects a user formigrating a repeating transaction and/or selects a repeating transactionfor migrating in response to the user's transaction data satisfying atransaction metric associated with the repeating transaction (e.g.,associated by transaction type, by service provider 108, or the like).As used herein, a transaction metric may include a measurable orestimable quantity or unit of a repeating transaction that can be usedto select a user and/or a repeating transaction for migrating to adifferent service provider 108. A transaction metric, in variousembodiments, may include a lifetime value metric, a total spend metric,a transaction interval metric, an interest rate for a repeatingtransaction, a sum total spent on a repeating transaction, a price perrepeating transaction, a monthly payment amount for a repeatingtransaction, a profit margin for a repeating transaction, a fee for arepeating transaction, a geographical transaction metric, an incomemetric for a user associated with a repeating transaction, a savingsmetric associated with a repeating transaction, and/or the like.

A transaction metric, in one embodiment, comprises a lifetime valuemetric indicating a projected and/or estimated total value of a user toa different service provider 108 to which a repeating transaction ismigrated (e.g., based on the user's aggregated set of transactionsand/or on a cost of the migration to the different service provider108), or the like. For example, an aggregation module 104 may determineand/or estimate, based on a user's aggregated set of transactions, anamount the user is likely to spend on subsequent instances of therepeating transaction (e.g., based on previous costs and/or profitsassociated with the repeating transaction), how loyal a user is likelyto be to the different service provider 108 after the migration (e.g.,based on a determined amount of time the user has used the previousservice provider 108, how often the user has previously migrated therepeating transaction, or the like), or the like, and may determine alifetime value metric based on one or more of the foregoingdeterminations.

A transaction metric, in certain embodiments, comprises a total spendmetric indicating a confidence of whether a user's aggregated set oftransactions includes each of the user's transactions of an associatedtransaction type (e.g., each of the user's financial transactions frommultiple financial institutions 108 for aggregated financial data, eachof the user's social media posts from multiple social media networks 108for aggregated social media data, or the like), aggregated from multipleentities (e.g., banks, credit unions, credit card companies or otherlenders, payment processing companies, online payment providers, and/orthe like for financial transaction events). If there is a low confidenceor probability that an aggregation module 104 has access to each of theuser's transactions of a certain type (e.g., a complete and/orsubstantially complete financial snapshot for the user for aggregatedfinancial transactions), it may be unlikely that an aggregation module104's determination of whether the user's financial transaction datasatisfies a transaction metric associated with a repeating transactionis accurate, and a new service provider 108 may therefore find the usera poor candidate for the migrating the repeating transaction, due to theuncertainty of whether the user's aggregated transaction data iscomplete. Conversely, if there is a high confidence or probability thatan aggregation module 104 has access to each of a user's transactionsfor the user of a transaction type (e.g., a complete and/orsubstantially complete financial snapshot for the user for aggregatedfinancial transactions), a new service provider 108 may have greatertrust in an aggregation module 104's selection of the user, and mayprompt the user to migrate the repeating transaction with greatercertainty.

An aggregation module 104, in certain embodiments, may analyze and/orprocess a user's aggregated set of transactions using one or more rules,flags, indicators, and/or the like, to determine a total spend metricindicating a confidence of whether the user's aggregated set oftransactions includes each of the user's transactions of a transactiontype (e.g., over a predefined period). For example, in one embodiment,an aggregation module 104 may start at a default confidence level (e.g.,50%, 0.5, 0%, 0, 100%, 1, or the like) and may adjust the confidencelevel for a user's aggregated set of transactions based on one or moreconfidence factors. An aggregation module 104, in certain embodiments,may decrease a confidence level if one transaction in a transaction pair(e.g., two transactions that are often seen together within a predefinedperiod) is missing, may increase a confidence level if both transactionsin a transaction pair are present, or the like. For example, atransaction pair may include a mortgage payment and a utility payment; apayment credit on a credit card statement and a corresponding debit froma bank account; a car payment and fuel purchases; and/or anothertransaction pair.

In a further embodiment, an aggregation module 104 may increase aconfidence level of a total spend metric if one or more predefined keytransactions are present, and/or may decrease a confidence level of atotal spend metric if one or more predefined key transactions are notpresent in the aggregated set of transactions for a user. A keytransaction, in one embodiment, comprises a transaction that is expectedto occur for each user within a predefined period. For example, a keytransaction may comprise a direct deposit and/or payroll check deposit,a mortgage and/or rent payment, at least a threshold amount spent on apersonal necessity (e.g., food), and/or another expected event ortransaction. In certain embodiments, an aggregation module 104 may beconfigured to prompt a user to add one or more additional accounts forone or more additional service providers 108 in response to determininga confidence level below a threshold for a total spend metric for theuser. In another embodiment, an aggregation module 104 may query a userwhether the user's aggregated set of transactions includes each of theuser's transactions for a transaction type, and may base a confidencelevel of a total spend metric on the user's answer.

An aggregation module 104, in one embodiment, may determine a confidencelevel of a total spend metric and/or another transaction metric byprocessing users' aggregated set of transactions using one or morepredefined rules, or the like. In a further embodiment, an aggregationmodule 104 may determine a confidence level of a total spend metricand/or another transaction metric dynamically, using machine learning orother artificial intelligence, or the like, causing an accuracy of anaggregation module 104's determinations to increase over time (e.g., atleast up to a point) as an aggregation module 104 learns from anddetects patterns in the aggregated set of transactions.

A geographical transaction metric, in various embodiments, may indicate,based on a user's aggregated transaction data, a geographical locationof a user, of a repeating transaction, of a current service provider 108for a repeating transaction, or the like. A geographic region, incertain embodiments, may comprise a street, a development, a district, acity, a county, a state, and/or another identifiable geographic area.

A transaction metric, in one embodiment, may comprise an income metricindicating a user's income (e.g., monthly, yearly, by source, grossincome, disposable income, and/or the like). In a further embodiment, atransaction metric may comprise a savings metric indicating an amount ofmoney a user saves (e.g., balance of a savings account; balance of aninvestment account; aggregated total of several savings and/orinvestment accounts; total amount saved; amount saved over a time periodsuch as daily, weekly, monthly, and/or yearly; a rate of saving; and/orthe like).

A transaction metric, in one embodiment, comprises a consistency metricindicating an amount of variation in spending for different transactionsin a series of repeating transactions. A transaction metric, in certainembodiments, may comprise a transaction interval metric indicating anamount of time spanned by a user's aggregated set of transactions (e.g.,one month, two months, three months, six months, a year, two years,three years, and/or the like). For example, in one embodiment, a newservice provider 108 for a long term or high valued repeatingtransaction, may prefer to prompt one or more users with a highertransaction interval metric (e.g., with a longer amount of time spannedby the users' aggregated set of transactions), while a new serviceprovider 108 for a smaller value repeating transaction, may not havesuch a preference and my prompt users with a lower transaction intervalmetric (e.g., with a shorter amount of time spanned by the users'aggregated set of transactions).

In certain embodiments, an aggregation module 104 may provide aninterface (e.g., a graphical user interface (GUI), an applicationprogramming interface (API), a command line interface (CLI), and/or thelike) for an administrator or other user associated with a serviceprovider 108 to set one or more thresholds whereby a user's aggregatedset of transactions may satisfy a transaction metric for migrating arepeating transaction to the service provider 108. By setting one ormore thresholds whereby a user's aggregated set of transactions maysatisfy a transaction metric, a service provider 108 may target certainusers for migrating repeating transactions based on the users' historyof transactions. An aggregation module 104, in one embodiment, may allowa service provider 108 to select a cap and/or a minimum on a number ofusers that will receive a prompt to migrate a repeating transaction, toadjust one or more thresholds of a transaction metric until at least aminimum number of users are selected, and/or the like.

FIG. 2 depicts one embodiment of an aggregation module 104. In thedepicted embodiment, the aggregation module 104 includes anauthentication module 202, a direct access module 204, and an interfacemodule 206.

In one embodiment, the authentication module 202 receives a user'selectronic credentials for a third party service provider 108 from theuser on a hardware device 102 of the user. In a further embodiment, theauthentication module 202 may receive electronic credentials for adifferent user (e.g., from a different hardware device 102, from abackend aggregation module 104, or the like), which may be encryptedand/or otherwise secured, so that the direct access module 204 maydownload data for the different user (e.g., downloading data formultiple users from a single user's hardware device 102).

For example, in the system 100, if one user's hardware device 102 isturned off, asleep, out of battery, blocked by a third party serviceprovider 108, or the like, in certain embodiments, an aggregation module202 on a different user's hardware device 102 and/or on a backendhardware server 110 may download data for the one user, using the oneuser's electronic credentials, and may send the data to the one user'shardware device 102, may send an alert and/or push notification to theone user's hardware device 102, or the like. In this manner, in oneembodiment, a user may continue to aggregate data, receive alerts and/orpush notifications, or the like, even if the user's own hardware device102 is blocked, unavailable, or the like. In cooperation with one ormore authentication modules 202, the aggregation modules 104 a, 104 b,in certain embodiments, may communicate with each other using a secureand/or encrypted protocol, and/or may store electronic credentials in asecure and/or encrypted manner, so that a user may not see and/or accessanother user's electronic credentials, downloaded data, or other privateand/or sensitive data.

In embodiments where an aggregation module 104 comprises hardware (e.g.,a semiconductor integrated circuit device such as an FPGA, an ASIC, orthe like), the authentication module 202 may comprise dedicated securityhardware for storing and/or processing electronic credentials,downloaded data, and/or other sensitive and/or private data, such as asecure cryptoprocessor (e.g., a dedicated computer on a chip ormicroprocessor embedded in a packaging with one or more physicalsecurity measures) which does not output decrypted data to an unsecurebus or storage, which stores cryptographic keys, a secure storagedevice; a trusted platform module (TPM) such as a TPM chip and/or TPMsecurity device; a secure boot ROM or other type of ROM; anauthentication chip; or the like. In another embodiment, theauthentication module 202 may store and/or process electroniccredentials, downloaded data, and/or other sensitive data in a secureand/or encrypted way using software and/or hardware of a user's existinghardware device 102 (e.g., encrypting data in RAM, NAND, and/or othergeneral purpose storage) with or without dedicated security hardware. Incertain embodiments, the authentication module 202 may encrypt and/orsecure data (e.g., electronic credentials, downloaded data) associatedwith a first user that is received by, processed by, and/or stored by asecond (e.g., different) user's hardware device 102 (e.g., from thefirst user's hardware device 102 over the data network 106 or the like),preventing the second user from accessing the first user's data whilestill allowing the first user's data to be downloaded and/or aggregatedfrom a different user's hardware device 102.

In one embodiment, as described above, electronic credentials maycomprise one or more of a username and password, fingerprint scan,retinal scan, digital certificate, personal identification number (PIN),challenge response, security token, hardware token, software token, DNAsequence, signature, facial recognition, voice pattern recognition,bio-electric signals, two-factor authentication credentials, or otherinformation whereby the authentication module 202 may authenticateand/or validate an identity of and/or an authorization of a user.

The authentication module 202, in certain embodiments, may receivedifferent credentials from a user for different accounts of the userwith different third party service providers 108 (e.g., differentecommerce sites or other online retailers or service providers,different social networks, different photo sharing sites, differentfinancial institutions) so that the aggregation module 104 may download,aggregate, and/or combine the user's data from the multiple differentthird party service providers 108. In one embodiment, as described belowwith regard to the password manager module 306 of FIG. 3, theauthentication module 202, instead of and/or in addition to receivingone or more passwords or other electronic credentials from a user, maymanage and/or determine one or more passwords or other electroniccredentials for a user for one or more third party service providers108. For example, in certain embodiments, the authentication module 202may receive an initial set of electronic credentials (e.g., a usernameand a password) from a user for an account of the user with a thirdparty service provider 108, and the authentication module 202 may usethe initial set of electronic credentials to access the user's accountwith the third party service provider 108 to set a new password,determined by the authentication module 202. The authentication module202, in one embodiment, may determine passwords or other electroniccredentials that are more secure than those typically created by and/ormemorable to a user (e.g., longer, more numbers, greater variationbetween capital and lowercase letters, more frequently changed, or thelike).

In one embodiment, the direct access module 204 accesses one or moreservers 108 of one or more third party service providers 108, from ahardware device 102 of a user and/or from a backend hardware server 110,using a user's electronic credentials from the authentication module 202(e.g., for the user associated with the hardware device 102, for adifferent user, or the like). The direct access module 204, in certainembodiments, downloads data associated with a user (e.g., a user'ssocial media posts, a user's photos, a user's financial transactions, orthe like) from one or more servers 108 of one or more third partyservice providers 108 to a hardware device 102 of a user (e.g., of theuser associated with the downloaded data, of a different user forprocessing and/or for transfer to the hardware device 102 of the userassociated with the downloaded data, or the like) and/or to a backendhardware server 110 associated with the direct access module 204,instead of or in addition to downloading the data directly to a hardwaredevice 102 of the user (e.g., based on an availability of the hardwaredevice 102 of the user, to backup the data in a second location, or thelike).

The direct access module 204, in certain embodiments, may use a webpageinterface of a server 108 of a third party service provider 108 toaccess the server 108 using a user's electronic credentials and/or todownload data associated with the user. For example, in certainembodiments, the direct access module 204 may download/load a webpagefrom a server 108 of a third party service provider 108, enter ausername and password or other electronic credentials for a user intotextboxes in a form on the webpage, submit the username and password orother electronic credentials using a submit button or other interfaceelement of the webpage, and/or otherwise submit electronic credentialsusing a website to gain authorized access to data on the server 108associated with the user. As described below, the pattern module 308 mayreceive and/or provide instructions enabling the direct access module204 to access a server 108 (e.g., a location or method for submittingelectronic credentials, or the like).

In response to successfully authenticating with and accessing a server108 of a third party service provider 108 with a user's electroniccredentials, the direct access module 204 may download data associatedwith the user (e.g., from a user's account or the like) from the server108, to a hardware device 102 associated with the user, to a backendhardware server 110, to a hardware device 102 of another userdownloading the data in proxy for the user, or the like. As describedbelow, in certain embodiments, the pattern module 308 may receive and/orprovide instructions enabling the direct access module 204 to downloaddata associated with a user from a server 108 of a third party serviceprovider 108 (e.g., a URL or other link to a location for the data, alabel or other identifier for locating the data within one or morewebpages or other data structures, or the like). The direct accessmodule 204, in certain embodiments, may follow instructions from apattern module 308 to authenticate and/or access data from one or morewebpages from a server 108 in a screen scraping manner, parsing one ormore webpages to locate an entry location and/or submit electroniccredentials; to locate, download, and/or extract data associated with auser; or the like.

In one embodiment, the direct access module 204 sends or otherwisesubmits electronic credentials and/or receives or otherwise downloadsdata using an API or other access protocol of a server 108 of a thirdparty service provider 108. For example, the direct access module 204may send a request in a format specified by and/or compatible with aserver 108 (e.g., an API server 108) of a third party service provider108. The sent request may comprise electronic credentials for a user ora portion thereof (e.g., a username and/or a password), a subsequentrequest may comprise electronic credentials for a user or a portionthereof (e.g., in response to receiving an acknowledgment from theserver 108 for the first request, or the like), and/or the direct accessmodule 204 may use a different access protocol of a server 108.

In response to a request for data from the direct access module 204(e.g., in response to the direct access module 204 authenticating a userusing an access protocol of a server 108), a server 108 of a third partyservice provider 108 may send and/or return data associated with a user(e.g., in one or more messages, packets, payloads, as a URL or otherpointer to a location from where the direct access module 204 mayretrieve the data, or the like). The direct access module 204, invarious embodiments, may receive data associated with a user directlyfrom a server 108 of a third party service provider 108 over a datanetwork 106; may receive a pointer, URL or other link to a location ofdata associated with a user from a server 108 of a third party serviceprovider 108; may receive data associated with a user from anotherentity on a data network 106 (e.g., in response to a request from theserver 108 of the third party service provider 108 to the other entityor the like); or may otherwise receive data associated with a useraccording to an access protocol of a third party service provider 108.

In one embodiment, a third party service provider 108 provides a directaccess module 204 with an API or other access protocol. In a furtherembodiment, a direct access module 204 may act as a wrapper for and/or aplugin or extension of, an application of a third party service provider108 (e.g., a mobile application), and the application may have access toan API or other access protocol of the third party service provider 108.In another embodiment, a direct access module 204 may be configured touse an API or other access protocol in a same manner as an applicationof a third party service provider 108 (e.g., a mobile application),through observation of the application of the third party serviceprovider 108 or the like. In certain embodiments, a direct access module204 may cooperate with an application of a third party service provider108, a web browser through which a user accesses services of a thirdparty service provider 108, or the like to access data associated with auser (e.g., accessing data already downloaded by an application and/oruser, accessing a database or other data store of an application and/orweb browser, scanning and/or screen scraping a web page of a third partyservice provider 108 as a user accesses the web page, or the like).

The direct access module 204, in certain embodiments, may accessdifferent third party service providers 108 in different manners. Forexample, a first third party service provider 108 may grant the directaccess module 204 with access to an API or other access protocol, whilethe direct access module 204 may use a web page interface (e.g., screenscraping) to access and download data from a second third party serviceprovider 108, or the like. In one embodiment, a remote backend hardwareserver 110 may be associated with a first party service provider 108(e.g., a vendor and/or provider of an aggregation module 104) and thedirect access module 204 may download data associated with a user fromboth the first party service provider 108 and from one or more thirdparty service providers 108, aggregating the data together so that theuser may access the data in a single interface and/or application. Forexample, as described below with regard to the interface module 206, theinterface module 206 may provide a user access to the user's photos frommultiple third party cloud storage providers 108 within a single photoapplication, may provide a user with access to the user's personalfinancial information within a single personal financial managementapplication and/or online banking application, may provide a user withaccess to posts from multiple social networks within a single socialnetworking application, or the like.

The direct access module 204, in certain embodiments, may storedownloaded and/or aggregated data independently from the one or morethird party service providers 108. For example, the direct access module204 may store a user's downloaded and/or aggregated data on a hardwaredevice 102 of the user, on a backend hardware server 110 accessible bythe user, or the like. In this manner, in certain embodiments, a usermay control and/or access the user's data, even if a third party serviceprovider 108 closes down or is not available, may use the user's data inany manner desired by the user even if the use is not supported by athird party service provider 108, or the like.

In one embodiment, the interface module 206 provides a user's datadownloaded by the direct access module 204, from a hardware device 102of a user (e.g., of the user associated with the downloaded data, of adifferent user) to another entity, such as a hardware device 102 of auser associated with the downloaded data (e.g., in response to the databeing downloaded by a hardware device 102 of a different user, from onehardware device 102 of a user to another hardware device 102 of the sameuser), a remote server 110 unaffiliated with (e.g., not owned by,operated by, controlled by, or the like) the third party serviceprovider 108 from which the data was downloaded, or the like. Forexample, the interface module 206 may provide an API or other interfaceto provide a user's downloaded and/or aggregated data to a hardwaredevice 102 of the user, to a backend aggregation module 104 b, to abackend hardware server 110, to a different third party service provider108, to a different/second hardware device 102 of the user, or the like.

In certain embodiments, it may be transparent and/or substantiallytransparent to a user which hardware device 102, 110 has downloaded dataassociated with the user. For example, the interface module 206 mayprovide downloaded data associated with a user from one hardware device102 of the user to another hardware device 102 of the user, from ahardware device 102 of the user to a backend hardware server 110 (e.g.,from which the user may access the data using a web browser, anapplication, or the like), from a backend hardware server 110 to ahardware device 102 of the user, or the like, allowing the user toaccess the data from a different location than the location to which thedata was downloaded.

In certain embodiments, the interface module 206 provides a GUI on ahardware device 102 of a user, and provides downloaded data associatedwith the user to the user through the GUI (e.g., allowing the user toview the data directly, providing one or more notifications and/orrecommendations to the user based on the data, providing one or moretables or charts to the user based on the data, providing a summary ofor one or more statistics related to the data, or the like). Theinterface module 206, in various embodiments, may provide a GUI to theuser from the same hardware device 102 to which the data was downloaded,on a different hardware device 102 than the hardware device 102, 110 towhich the data was downloaded, or the like.

For example, in one embodiments, where the data associated with a usercomprises photos, the interface module 206 may provide a photomanagement interface, a photo editing interface, or the like wherein theuser may view and/or otherwise access the user's downloaded and/oraggregated photos. In a further embodiment, where the data associatedwith a user comprises the user's financial transaction history (e.g.,purchases and/or other financial transactions downloaded from one ormore ecommerce sites 108 or other online retailers 108 or serviceproviders 108; one or more financial institutions 108 such as banks,credit unions, lenders, or the like; and/or another entity), theinterface module 206 may provide a personal financial managementinterface, with a list of transactions (e.g., with item level dataidentifying multiple individual items within a single purchase), one ormore budgets, one or more financial goals, a debt management interface,a net worth interface, and/or another personal financial managementinterface wherein the user may view the user's downloaded and/oraggregated financial transaction history, and/or alerts orrecommendations based thereon. In another embodiment, where the dataassociated with a user comprises social media posts, the interfacemodule 206 may provide a GUI comprising a stream, feed, and/or wall ofsocial media posts for the user to view (e.g., downloaded and/oraggregated social media posts from multiple social networks 110, fromdifferent contacts or friends of the user, or the like).

FIG. 3 depicts another embodiment of an aggregation module 104. In thedepicted embodiment, the aggregation module 104 includes anauthentication module 202, a direct access module 204, and an interfacemodule 206 and further includes a route module 314, a frequency module316, and a test module 318. The authentication module 202, in thedepicted embodiment, includes a local authentication module 302, anetwork authentication module 304, and a password manager module 306.The direct access module 204, in the depicted embodiment, includes apattern module 308, an access repair module 310, and a hierarchy module312.

In one embodiment, the local authentication module 302 secures and/orauthenticates the user's access to downloaded data, to stored passwords,and/or other data on a user's hardware device 102, transferred to and/orfrom a user's hardware device 102, or the like. For example, the localauthentication module 302 may cooperate with one or more security and/orauthentication systems of the user's hardware device 102, such as a PIN,password, fingerprint authentication, facial recognition, or otherelectronic credentials used by the user to gain access to the hardwaredevice 102. In a further embodiment, the local authentication module 302may authenticate a user before allowing the interface module 206 toprovide the user access to downloaded/aggregated data and/or alerts orother messages. For example, the local authentication module 302 maymanage and/or access electronic credentials associated with theaggregation module 104, for a user, and may authenticate the user inresponse to the user accessing an application and/or service of theaggregation module 104.

In certain embodiments, the local authentication module 302 may encryptand/or otherwise secure, on a user's hardware device 102, electroniccredentials and/or downloaded data associated with a different user, sothat the user may not access data associated with the different user,but the different user may access the data once it is transmitted to ahardware device 102 of the different user, to a backend hardware server110, or the like. Local authentication modules 302 of different hardwaredevices 102, 110 may cooperate to securely transfer data (e.g., one ormore electronic credentials, downloaded data, or the like) over the datanetwork 106, from one hardware device 102, 110 to another hardwaredevice 102, 110. In a further embodiment, the local authenticationmodule 302 may ensure that a user's electronic credentials and/ordownloaded data remain on a single hardware device 102 (e.g., are nottransmitted on a data network 106), in a secure repository or the like,and are not stored on and/or accessible to a backend hardware server110, a hardware device 102 of another user, or the like.

In one embodiment, the network authentication module 304 receives and/orstores a user's electronic credentials for one or more third partyservice providers 108 on a hardware device 102 of the user, on a backendhardware server 110, or the like. The network authentication module 304,in various embodiments, may receive a user's electronic credentials fromthe user, from a hardware device 102 of the user, from a backendhardware server 110, or the like. The network authentication module 304may cooperate with the direct access module 204 to provide a user'selectronic credentials to a server 108 of a third party service provider108 (e.g., the network authentication module 304 may provide electroniccredentials to the direct access module 204 to provide to a server 108,the network authentication module 304 may provide electronic credentialsdirectly to a server 108, or the like).

The network authentication module 304, in certain embodiments, maycooperate with the local authentication module 302 to encrypt and/orotherwise secure a user's electronic credentials for one or more thirdparty service providers 108, on a hardware device 102 of a user, on adata network 106, on a hardware device 102 of a different user, on abackend hardware server 110, while being provided to a server 108 of athird party service provider 108, or the like. In a further embodiment,the network authentication module 304 ensures that a user's electroniccredentials are only stored on a user's hardware device 102 and sentfrom the user's hardware device 102 to a server 108 of a third partyservice provider 108, and does not store a user's electronic credentialson a backend hardware server 110, on a different user's hardware device102, or the like. In another embodiment, the network authenticationmodule 304 may securely store (e.g., using secure encryption) a user'selectronic credentials for a third party service provider 108 on abackend hardware server 110, on a different user's hardware device 102,or the like, so that a direct access module 204 may access and/ordownload data associated with the user, even if the hardware device 102of the user is unavailable, blocked, or the like, as described belowwith regard to the route module 314. In certain embodiments, whether thenetwork authentication module 304 and/or the local authentication module302 allow electronic credentials to be sent to and/or stored by adifferent user's hardware device 102, a backend hardware server 110, orthe like may be based on a setting defined based on user input, so thatthe user may decide a level of security, or the like.

In one embodiment, the password manager module 306 may manage and/orstore electronic credentials of a user for a plurality of third partyservice providers 108, so that the direct access module 204 may accessand/or download data associated with the user from each of the pluralityof third party service providers 108. The password manager module 306,in certain embodiments, may generate and/or otherwise manage different,secure, credentials for each of a plurality of third party serviceproviders 108.

The password manager module 306, in one embodiment, may securely storegenerated credentials for a user on a hardware device 102 of the user,so that the user does not have to remember and enter the generatedelectronic credentials. For example, in addition to allowing a directaccess module 204 to access a third party service provider 108 usinggenerated electronic credentials, the password manager module 306 mayautomatically populate one or more interface elements of a form on awebpage with electronic credentials (e.g., a username, a password) ofthe user, in response to the user visiting the web page in a webbrowser, or the like, without the user manually entering the electroniccredentials. The password manager module 306, in certain embodiments,may periodically update (e.g., regenerate different credentials, such asa different password, and update the user's account with the third partyservice provider 108 with the regenerated different credentials)electronic credentials for a user, such as every week, every month,every two months, every three months, every four months, every fivemonths, every six months, every year, every two years, in response to auser request, in response to a request from a third party serviceprovider 108, and/or over another time period or in response to anotherperiodic trigger.

The password manager module 306, in one embodiment, may synchronize auser's electronic credentials (e.g., provided by the user, generated bythe password manager module 306, or the like) across different hardwaredevices 102, web browsers, or the like of a user. For example, inresponse to a password manager module 306 and/or the user updating orotherwise changing electronic credentials, the password manager module306 may propagate the update/change to one or more other passwordmanager modules 306, on different hardware devices 102 of the user, orthe like.

In one embodiment, the pattern module 308 determines an ordered list ofmultiple locations on a server 108 of a third party service provider 108for the direct access module 204 to access the server (e.g., which mayinclude locations other than where the data of the user is stored and/oraccessible), one or more delays for the direct access module 204 to waitbetween accessing locations on the server 108, or the like. The patternmodule 308, in one embodiment, may determine and/or select the multiplelocations and/or the one or more delays based on an average patternidentified in behavior of multiple users accessing a third party serviceprovider 108 using a web browser. In a further embodiment, the patternmodule 308 determines and/or selects the multiple locations and/or theone or more delays based on a pattern identified in behavior of the userassociated with the hardware device 102 on which the pattern module 308is disposed, accessing the third party service using a web browser ofthe user's hardware device 102.

In one embodiment, the access repair module 310 detects that access to aserver 108 of a third party service 108 and/or data associated with auser is broken and/or inaccessible. The access repair module 310, incertain embodiments, provides an interface to a user allowing the userto graphically identify an input location for the user's electroniccredentials, a location of data associated with the user, or the like.The access repair module 310, in one embodiment, processes one or morepages of a server 108 and displays to a user in an interface an estimateof an input location for the user's electronic credentials, a locationof data associated with the user, or the like so that the user mayconfirm whether or not the estimate is correct using the interface.

In one embodiment, the test module 318 cooperates with the access repairmodule 310, and attempts to access a server 108 of a third party serviceprovider 108 for a plurality of different users (e.g., a sample group ortest set), based on an identification from a single user, usingelectronic credentials of the different users or the like. The testmodule 318, in certain embodiments, determines whether data associatedwith the different users (e.g., a sample group or test set) isaccessible using the identification from the single user. The testmodule 318, in one embodiment, provides the identification from a userto other instances of the direct access module 204 for accessing aserver 108 of a third party service provider 108 in response to anamount of the different users (e.g., a sample group or test set) forwhich data is accessible using the identification from the single usersatisfying a threshold.

In one embodiment, the hierarchy module 312 provides the direct accessmodule 204 with an ordered list of multiple different sets ofinstructions for accessing a server 108 of a third party service 108using a user's electronic credentials, for downloading data associatedwith the user, or the like. Each different set of instructions, incertain embodiments, comprises a location for entering a user'selectronic credentials, an instruction for submitting the user'selectronic credentials, one or more locations of the data associatedwith the user, or the like.

In one embodiment, the route module 314 determines whether a hardwaredevice 102 of a user is available for the direct access module 204 todownload data associated with the user from a server 108 of a thirdparty service provider 108. The route module 314, in certainembodiments, may access a server 108 of a third party service provider108, from a remote backend hardware server 110, using the user'selectronic credentials, to download data associated with the user fromthe server 108 to the remote backend hardware server 110 in response tothe route module 314 determining that the hardware device 102 of theuser is unavailable. The route module 314, in one embodiment, provides auser one or more alerts on a hardware device 102 of the user based onthe data associated with the user downloaded to the remote backendhardware server 110.

In one embodiment, the frequency module 316 sets a frequency with whichthe direct access module 204 accesses the server 108 of a third partyservice provider 108. The frequency module 316, in certain embodiments,determines a frequency based on input from a remote backend hardwareserver 110, which may be unaffiliated with the third party serviceprovider 108 being accessed, so that the remote backend hardware server110 (e.g., the frequency module 316 executing on the remote backendhardware server 110) determines frequencies for a plurality of directaccess modules 204 for different users and different hardware devices102. In a further embodiment, the frequency module 316 determines afrequency based on input from a user, allowing the user to set theaccess frequency. The frequency module 316, in certain embodiments,limits an access frequency to prevent inadvertent denial of service by athird party service provider 108, or the like.

FIG. 4A depicts one embodiment of a system 400 for item level dataaggregation. The system 400, in the depicted embodiment, includes one ormore user hardware devices 102 with one or more aggregation modules 104a, and one or more backend hardware servers 110 comprising one or morebackend aggregation modules 104 b. An authentication module 202 of anaggregation module 104 a, in certain embodiments, may securely provideencrypted user credentials for a user from the user's hardware device102 to a backend aggregation module 104 b (e.g., an authenticationmodule 202 of the backend aggregation module 104 b) on a backendhardware server 110, over the data network 106 or the like, so that adirect access module 204 of the backend aggregation module 104 b mayaccess one or more third party service providers 108 from the backendhardware server 110 (e.g., over the data network 106) to download dataassociated with the user.

For example, the backend hardware server 110 may download data for theuser by default, in response to the user's hardware device 102 a beingpowered off, being asleep, being blocked from accessing one or morethird party service providers 108, or the like, as determined by a routemodule 314, or the like. The interface module 206 of the backendaggregation module 104 b may provide one or more alerts/messages to theuser based on the downloaded data and/or may provide the downloaded datato the user (e.g., in response to the user's hardware device 102 abecoming available, to a different hardware device 102 associated withthe first user, directly from the backend hardware server 110 as a webpage and/or through a dedicated application, or the like).

FIG. 4B depicts one embodiment of a system 402 for item level dataaggregation. The system 402, in the depicted embodiment, includes asingle user hardware device 102 with an aggregation module 104 a. Anauthentication module 202 of the aggregation module 104 a, in certainembodiments, may store and/or manage electronic user credentials locallyon the user's hardware device 102, the direct access module 204 mayaccess one or more third party service providers 108 directly from theuser's hardware device 102 (e.g., over the data network 106) to downloaddata associated with the user to the user's hardware device 102, theinterface module 206 may provide the data and/or one or morealerts/messages based on the data to the user from the user's hardwaredevice 102, or the like. In the depicted system 402, the aggregationmodule 104 a may create a local repository of data for the user from oneor more third party service providers 108, on the user's hardware device102, without providing the user's credentials, the user's data, or thelike to a different user's hardware device, to a backend hardware server110, or the like.

FIG. 4C depicts one embodiment of a system 404 for item level dataaggregation. The system 404, in the depicted embodiment, includes aplurality of user hardware devices 102 with aggregation modules 104 a,associated with different users. In certain embodiments, a firstaggregation module 104 a (e.g., an authentication module 202 of thefirst aggregation module 104 a) may securely provide encrypted usercredentials for a first user from the first user's hardware device 102 ato a second aggregation module 104 a (e.g., an authentication module 202of the second aggregation module 104 a), over the data network 106 orthe like, so that a direct access module 204 of the second aggregationmodule 104 a may access one or more third party service providers 108from the second user's hardware device 102 b (e.g., over the datanetwork 106) to download data associated with the first user.

For example, the second user's hardware device 102 b may download datafor the first user in response to the first user's hardware device 102 abeing powered off, being asleep, being blocked from accessing one ormore third party service providers 108, or the like, as determined by aroute module 314, or the like. The interface module 206 of the secondaggregation module 104 a may provide one or more alerts/messages to thefirst user based on the downloaded data and/or may provide thedownloaded data to the first user (e.g., in response to the first user'shardware device 102 a becoming available, to a different hardware device102 associated with the first user, to a backend hardware server 110 towhich the first user has access, or the like). As described above, incertain embodiments, the authentication module 202, the direct accessmodule 204, the interface module 206, and/or the route module 314 mayencrypt and/or otherwise secure data for the first user (e.g., the firstuser's electronic credentials, downloaded data associated with the firstuser, alerts/messages for the first user), so that it is difficult orimpossible for the second user to access the data for the first user,thereby preventing and/or minimizing unauthorized access to the firstuser's data while providing greater flexibility in devices 102 and/orlocations from which data for the first user may be downloaded.

FIG. 5A depicts one embodiment of a user interface 500. The interface500, in certain embodiments, is provided by an access repair module 310to a user on an electronic display screen of a hardware device 102,allowing a user to graphically identify one or more input locations forthe user's credentials (e.g., a location for a username, a location fora password, or the like), a method for sending and/or submitting theuser's credentials (e.g., an API specification, a location of a submitbutton, or the like), a location of data associated with the user (e.g.,a URL or other link; a location on a web page at a link; a label, tag,or other identifier within plain text and/or source code of a web page506; or the like) and/or to graphically identify one or more otherinstructions for accessing data associated with the user from a thirdparty service provider 108.

In the depicted embodiment, the access repair module 310 overlays aninterface 502 over one or more pages of a website 506 of a third partyservice provider 108 on an electronic display screen of a user'shardware device 102. As described above, in various embodiments, theaccess repair module 310 may comprise a browser plugin and/or extensionwhich provides an interface 502 within an internet browser, may comprisean embedded browser within an application of the access repair module310, or may otherwise be integrated with and/or in communication with aninternet browser.

The access repair module 310, in the depicted embodiments, determinesand/or displays one or more suggestions 504 and/or recommendations 504for the user, which the user may either confirm or change/correct. Forexample, the access repair module 310 may display an interface element504 a with a suggested location for the user to enter a user name, aninterface element 504 b with a suggested location for the user to entera password, an interface element 504 c with a suggested credentialsubmit action, an interface element 504 d with a suggested location ofdata associated with the user, and/or one or more other interfaceelements allowing a user to graphically identify one or more locationswithin a website 506 of a third party service provider 108.

In one embodiment, an interface element 504 may include one or moreidentifiers of an estimated location and/or action which the accessrepair module 310 has determined (e.g., by scanning and/or parsing oneor more pages of a website 506, based on input from other usersaccessing one or more pages of a website 506, based on previousinteractions of the user with one or more pages of a website 506, aprediction made using a machine learning and/or artificial intelligenceof a website 506, based on a statistical analysis of historical changesto one or more pages of a website 506 and/or of one or more similarwebsites, or the like), such as an arrow or other pointer to a location;a link or other identifier of a location; a box or other highlightingaround a location; altering text labeling for a location to make thetext bold, italic, and/or underlined; or the like. A user, in certainembodiments, may click, select, or otherwise identify a location toeither confirm or change/correct a location suggested by the accessrepair module 310. For example, a user may click or otherwise select aninterface element 504 associated with a location and/or action (e.g., toactivate the selected interface element 504) and may click or otherwiseselect the location and/or perform the action, which the access repairmodule 310 may record (e.g., automatically populating a text fieldidentifying the location and/or action, recording a macro allowing theaction to be automatically repeated without the user, or the like).

The user, in one embodiment, may interact with the website 506 in orderto locate and/or identify one or more locations, perform one or moreactions, or the like. For example, in certain embodiments, the user maynavigate to one or more different pages within the website 506, maylogin to the website 506 using the user's electronic credentials for theweb site 506, may navigate to a different web site 506, may navigate toand/or download data associated with the user from the website 506, mayuse the website 506 in a usual manner, or the like. As described abovewith regard to the pattern module 308, the pattern module 308, in oneembodiment, may monitor the user's access pattern for the website 506,allowing the direct access module 204 to at least partially emulate theuser's access pattern in accessing the website 506, downloading dataassociated with the user from the website 506, or the like. In thedepicted embodiment, the access repair module 310 (and/or an associatedbrowser) displays a browser view of the website 506, with text, images,and/or other elements displayed substantially how an internet browserwould display the website 506, with the addition of the interface 502displayed over the website 506, to one side of the website 506, or thelike.

FIG. 5B depicts one embodiment of a user interface 510. While the userinterface 500 described above comprises a rendered, browser view of oneor more pages of a website 506, in one embodiment of the interface 510of FIG. 5B, the access repair module 310 (and/or an associated browser)displays source code 516 of a website 506. For example, in oneembodiment, the user interface 500 may comprise a standard access repairinterface and the user interface 510 may comprise an advanced accessrepair interface, allowing one or more advanced users to identify one ormore locations and/or actions within source code 516 of a website 506,which may not be visible and/or readily apparent in the website 506itself. In certain embodiments, a user may select and/or toggle betweena standard user interface 500 or view and an advanced user interface 510or view.

In the depicted embodiment, the access repair module 310 displays a userinterface 512 over and/or adjacent to the displayed source code 516,with one or more interface elements 514 a-d allowing a user to identifyone or more locations, actions, or the like substantially as describedabove. The access repair module 310, in the depicted embodiment,displays one or more suggestions and/or estimates of locations and/oractions, which the user may confirm and/or change/correct. In variousembodiments, a user may identify a location and/or an action in thesource code 516 by selecting and/or activating an interface element 514and selecting a portion of the source code 516, by dragging a portion ofthe source code 516 and dropping the portion onto an interface element514, by cutting and pasting a portion of the source code 516 into aninterface element 514, and/or otherwise identifying a location and/or anaction based on the source code 516.

In response to a user identifying one or more locations and/or actions(e.g., for entering, submitting, and/or sending electronic credentials;for locating and/or downloading data; or the like), in certainembodiments, the access repair module 310 may cooperate with the testmodule 318 to perform a live and/or real-time test of the identified oneor more locations and/or actions, to determine the validity and/oreffectiveness of the identified one or more locations and/or actionswhile the interface 500, 510 is visible to and/or in use by the user,allowing the user to change and/or correct provided information duringthe same session. For example, the access repair module 310 may displaya test button or other user interface element to a user, which the usermay select and/or activate to initiate a test. In another embodiment,the access repair module 310 may automatically perform a test inresponse to a user providing a location and/or action, without the userselecting and/or activating a test button or other user interfaceelement. In a further embodiment, the test module 318 may perform one ormore tests independent of the access repair module 310, with or withouttesting functionality of the access repair module 310.

FIG. 6A depicts one embodiment of an aggregated set of transactions 600and of item-level data 610 for transactions. The aggregated set oftransactions 600, in the depicted embodiment, comprises a list offinancial transactions (e.g., aggregated and/or downloaded for a creditcard, checking account, savings account, investment account, and/oranother financial account). In other embodiments, the set oftransactions 600 may comprise a data backup log with a list of databackup events for a hardware device 102 of a user, a security log with alist of antivirus scan events for a hardware device 102 of a user, anupdate log with a list of software update events for a hardware device102 of a user, an operating system log or other software log with a listof error events for a hardware device 102 of a user, or the like.

The aggregated set of transactions 600, in the depicted embodiment,includes an online order 602 from an online merchant, a purchase 604from a brick and mortar gas station, and a subscription payment 606 to astreaming video service. The item-level data 610, in the depictedembodiment, comprises an order history for an account of the user at theonline merchant from the online order 602. In other embodiments, theitem-level data 610 may comprise an invoice, an account statement, orthe like. The item-level data 610, in the depicted embodiment, includestwo items 614, 616 purchased as part of the same transaction, a skillet614 and an iron 616. The item-level data 610 includes names for theitems 614, 616, an order date for the items 614, 616, an image of eachitem 614, 616 (e.g., a downloadable image file), return information forthe items 614, 616, one or more attributes for the items 614, 616 (e.g.,physical dimensions, color, weight, or the like), a name of a seller orvendor, a description for the items 614, 616, user reviews for the items614, 616, user ratings for the items 614, 616, or the like. Anaggregation module 104, in certain embodiments, may follow one or morehyperlinks within the item-level data 610 in order to locate anddownload additional item-level data 610 (e.g., screen scraping andclicking a hyperlink within the listing of an item 614, 616 to locate animage file, a detailed description, user reviews, user ratings, or thelike).

In other embodiments, the item-level data 610 may be for the purchase604 from a brick and mortar gas station, or other brick and mortarretailer or entity. An aggregation module 104 may locate and downloadthe item-level data 610 from a user's online account for the brick andmortar entity (e.g., a loyalty or rewards program, a warranty program,an order history, an invoice, an account statement, or the like). Inanother embodiment, an aggregation module 104 a on a hardware device 102of a user may scan a printed receipt for the purchase 604 using anoptical sensor (e.g., a camera, a scanner, or the like) and may extractitem-level data 610 for the purchase 604 from the scanned printedreceipt using optical character recognition (OCR) or the like (e.g., ifitem-level data 610 is not available for the purchase 604 online, or thelike).

In a further embodiment, an aggregation module 104 a on a hardwaredevice 102 of a user may wirelessly communicate with a point of salesystem of the brick and mortar retailer or other entity todownload/receive the item-level data 610 (e.g., using near fieldcommunications (NFC), Bluetooth®, Wi-Fi, a radio frequency identifier(RFID), an infrared (IR) signal protocol, a radio frequency (RF) signalprotocol, or the like). For example, a point of sale system of the brickand mortar retailer or other entity may send a list of items purchased,purchase prices, or the like wirelessly to a hardware device 102 of auser in order for the user to make an electronic payment using thehardware device 102, or the like.

FIG. 6B depicts one embodiment of a graphical user interface 620, 630. Afirst graphical user interface 620 includes entries 622 for eachtransaction 602, 604, 606 and each entry 622 includes a user interfaceelement (e.g., a “+” sign, in the depicted embodiment), for receiving apredefined user input from a user relative to the associated transactionin the displayed set of transactions (e.g., clicking on the “+” sign toexpand an entry 622 to display the item-level data 614, 616, causing theaggregation module 104 to display the item-level information 614, 616and convert the “+” sign to a “−” sign).

In the depicted embodiment, an aggregation module 104 displaysidentifiers (e.g., image files, names, SKU identifiers, UPCs, EANs,GTINs, prices, categories, vendors, dates, or the like) for the items614, 616 associated with a transaction 602, 604, 606, in response todetecting the predefined user input from the user (e.g., a click, touch,swipe, keypress, voice command, button press, or the like) relative toan identified transaction. While the depicted embodiment includes items614, 616 purchased from an online merchant in the online order 602, inother embodiments, the graphical user interface 630 may includeitem-level data 614, 616 for the purchase 604 from a brick and mortargas station (e.g., for gasoline purchased, convenience or restaurantpurchases, or the like from a gas station), or other brick and mortarretailer or entity, item-level data 614, 616 for the payment 606 to theonline video streaming service or other third party service provider 108(e.g., a list of videos viewed for the month, subscription plan details,or the like), or the like.

In certain embodiments, items 614, 616 within a single transaction maybe from multiple categories (e.g., a fuel and a food purchase 604 at thesame gas station, or the like). An aggregation module 104 may split anidentified transaction into multiple categories (e.g., in a personalfinancial management and/or digital money management program for auser), based on the downloaded item-level data (e.g., categorizing afuel purchase in a transportation category and categorizing conveniencestore purchase in a food and/or shopping category, or the like).

FIG. 7 depicts one embodiment of a method 700 for item level dataaggregation. The method 700 begins and an aggregation module 104aggregates 702 a set of transactions for a user from a first data source(e.g., an aggregation server, a third party service provider 108, afinancial institution, or the like). An aggregation module 104identifies 704 a transaction made with a predefined third party (e.g., aretailer, a vendor, a business, a third party service provider 108,another entity, or the like) within the aggregated 702 set oftransactions.

An aggregation module 104 uses 706 electronic credentials for the userto login to an account of the user on a hardware server of the thirdparty. An aggregation module 104 downloads 708 item-level data for aplurality of transactions of the user from the hardware server of thethird party. An aggregation module 104 matches 710 one of the pluralityof downloaded 708 transactions to the identified 704 transaction (e.g.,based on a transaction amount, a transaction date, a party to thetransaction, an identifier for the transaction, or the like). Anaggregation module 104 associates 712 the downloaded 708 item-level datafor the matched 710 transaction from the hardware server of the thirdparty with the identified 704 transaction aggregated 702 from the firstdata source. Item-level data for the matched 710 transaction, in oneembodiment, identifies a plurality of items within the identified 704transaction.

An aggregation module 104 displays 714 the aggregated 702 set oftransactions to the user. In response to receiving predefined user inputfrom the user relative to the identified 704 transaction in thedisplayed 714 set of transactions, an aggregation module 104 displays716 identifiers for a plurality of items within the identified 704transaction to the user and the method 700 ends.

The present invention may be embodied in other specific forms withoutdeparting from its spirit or essential characteristics. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

What is claimed is:
 1. A method comprising: identifying a transactionmade with a third party within a set of transactions; using electroniccredentials for the user to login to an account of the user at the thirdparty; downloading item-level data from the third party that correspondsto the identified transaction in response to logging into the user'saccount at the third party, the item-level data identifying one or moreitems within the identified transaction; displaying the set oftransactions to the user; and displaying the item-level data for the oneor more items within the identified transaction to the user in responseto receiving input from the user relative to the identified transactionin the displayed set of transactions.
 2. The method of claim 1, furthercomprising splitting the identified transaction into multiplecategories, each of the multiple categories associated with at least oneitem of the plurality of items within the identified transaction.
 3. Themethod of claim 1, wherein the identified transaction comprises one ormore of a data backup event for a hardware device of the user over adata network, an antivirus scan event for a hardware device of the user,a software update event for a hardware device of the user, and an errorevent on a hardware device of the user and the plurality of itemscomprise one or more of a list of data objects backed up, a list ofsecurity threats, a list of software updates, and debug information. 4.The method of claim 1, further comprising updating at least a portion ofthe item-level data by re-downloading updated item-level data from thehardware server of the third party in response to a trigger, anddisplaying the updated item-level data to the user in response toreceiving the predefined user input.
 5. The method of claim 4, whereinthe updated item-level data comprises one or more of an image file forone of the plurality of items, a description for one of the plurality ofitems, and a rating for one of the plurality of items.
 6. The method ofclaim 1, wherein downloading the item-level data comprises parsing oneor more webpages from the hardware server of the third party associatedwith the account of the user to locate one or more of an invoice, anorder history, and an account statement comprising at least a portion ofthe item-level data.
 7. The method of claim 6, wherein downloading theitem-level data further comprises downloading supplemental dataassociated with the plurality of items in response to locating theplurality of items in the one or more of the invoice, the order history,and the account statement, the supplemental data comprising one or moreof image files, item descriptions, user ratings, and user reviews forthe plurality of items.
 8. The method of claim 1, wherein the identifiedtransaction comprises a purchase and the plurality of items compriseitems purchased in the identified transaction.
 9. The method of claim 8,wherein the item-level data comprises one or more of names, stockkeeping unit identifiers, universal product codes, international articlenumbers, and global trade item numbers for the plurality of items. 10.The method of claim 8, wherein the hardware server of the third partycomprises a point of sale system, the third party comprises a retailer,and downloading the item-level data from the hardware server of thethird party comprises receiving the item-level data at a mobile hardwaredevice of the user from the point of sale system using a wirelesscommunication protocol.
 11. The method of claim 1, further comprising:scanning a printed receipt associated with another transaction from theset of transactions using an optical sensor; extracting item-level datafor the other transaction from the scanned printed receipt using opticalcharacter recognition, the item-level data for the other transactionidentifying a plurality of items within the other transaction; anddisplaying identifiers for the plurality of items within the othertransaction to the user in response to receiving predefined user inputfrom the user relative to the other transaction in the displayed set oftransactions.
 12. The method of claim 11, further comprising downloadingsupplemental data associated with the plurality of items within theother transaction in response to extracting the plurality of itemswithin the other transaction from the printed receipt, the supplementaldata comprising one or more of image files, item descriptions, userratings, and user reviews for the plurality of items within the othertransaction.
 13. The method of claim 1, further comprising migratingpayment for one or more subsequent transactions with the third party,using the electronic credentials for the user, from a first serviceprovider to a different service provider, via the hardware server of thethird party in response to authorization from the user.
 14. The methodof claim 13, wherein migrating the payment for the one or moresubsequent transactions with the third party comprises: logging into awebsite of the hardware server of the third party using the electroniccredentials for the user; locating one or more user interface elementsassociated with the payment; and submitting payment informationassociated with the different service provider to the web site of thehardware server using the one or more user interface elements.
 15. Anapparatus comprising: a trusted hardware device authorized by a user touse a plurality of electronic credentials for the user, the trustedhardware device configured to: identify a transaction made with a thirdparty within a set of transactions; use electronic credentials for theuser to login to an account of the user at the third party; downloaditem-level data from the third party that corresponds to the identifiedtransaction in response to logging into the user's account at the thirdparty, the item-level data identifying one or more items within theidentified transaction; display the set of transactions to the user; anddisplay the item-level data for the one or more items within theidentified transaction to the user in response to receiving input fromthe user relative to the identified transaction in the displayed set oftransactions.
 16. The apparatus of claim 15, wherein downloading theitem-level data comprises parsing webpages from the third parties, thewebpages associated with the accounts of the user, to locate one or moreof an invoice, an order history, and an account statement comprising atleast a portion of the item-level data.
 17. The apparatus of claim 15,wherein the trusted hardware device downloads the item-level data for atleast one of the plurality of transactions from a point of sale systemfor one of the plurality of predefined third parties at the time of theone of the plurality of transactions using a wireless communicationsprotocol.
 18. A system comprising: a backend hardware server that:identifies a transaction made with a third party within a set oftransactions; uses electronic credentials for the user to login to anaccount of the user at the third party; and downloads item-level datafrom the third party that corresponds to the identified transaction inresponse to logging into the user's account at the third party, theitem-level data identifying one or more items within the identifiedtransaction; and an aggregation module located on a hardware device forthe user, the aggregation module configured to: display the set oftransactions to the user; and display the item-level data for the one ormore items within the identified transaction to the user in response toreceiving input from the user relative to the identified transaction inthe displayed set of transactions.
 19. The system of claim 18, whereinthe hardware server of the third party comprises a point of sale system,the third party comprises a retailer, and the aggregation module isfurther configured to download item-level data for another transactionwithin the set of transactions from the point of sale system to thehardware device for the user using a wireless communication protocol.20. The system of claim 18, wherein the aggregation module is furtherconfigured to: scan a printed receipt associated with anothertransaction from the set of transactions using an optical sensor of thehardware device for the user; extract item-level data for the othertransaction from the scanned printed receipt using optical characterrecognition, the item-level data for the other transaction identifying aplurality of items within the other transaction; and display identifiersfor the plurality of items within the other transaction to the user inresponse to receiving predefined user input from the user relative tothe other transaction in the displayed set of transactions.